Update README to remove maintenance notice#2246
Open
0xInnominatus wants to merge 1 commit into
Open
Conversation
Removed the note about Brownie no longer being actively maintained and suggested the Ape Framework for Python Ethereum development.
Author
|
@BobTheBuidler Hi Bob! Could you please share your thoughts on this topic? I’m planning to start a new project in the near future, and if Brownie is actively maintained again, I’d like to use this framework, especially since you’ve added mypyc support and I critically need high performance (Ape and Wake currently don’t support running with mypyc). What do you think? Can we expect the disclaimer about the lack of active maintenance to be removed from the README and documentation? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removed the note about Brownie no longer being actively maintained
What I did
Considering the frequency of releases and the active use of eth-brownie in many projects, including Yearn, maybe it makes sense to remove the mention that the framework is no longer actively maintained from docs and README? I personally use eth-brownie together with eth-wake quite actively and I am very happy to see that the good old tool is back.